-
Notifications
You must be signed in to change notification settings - Fork 26
Adds table to dynamic tag logic explanation #1749
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
🔍 Preview links for changed docs |
@@ -8,7 +8,7 @@ Specifically for versioned products, badges will display differently when the `a | |||
* `Deprecation planned` (if the lifecycle is deprecated) | |||
|
|||
Example: {applies_to}`stack: deprecated 99.99` | |||
* `Removal planned` (if the lifecycle is removed) | |||
* `Removal planned` (if the lifecycle is removed) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd remove these bullets in favor of the table below + kind of rework the content so it's introducing the table instead
|
||
| Lifecycle | Release status | Badge text | | ||
|-------------|----------------|-----------------------------------------------------------------------------------| | ||
| preview | prerelease | Planned | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
these can have examples too. just set the version to 99.99
:::{note} | ||
Visuals and wording in the output documentation are subject to changes and optimizations. | ||
::: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd also move this note down to the bottom
Overview
This PR adds a table to the section that explains the logic of dynamic badges for better understanding.